An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi, I am very frustrated with having my app repeatedly rejected for issues I can't fix because they don't exist. So I'm trying to publish this app that offers some consumable iAP that is used to unlock a pairing app on a 3rd party platform. Originally the app did not have an account system, it was rejected by Apple on the grounds that the user may want to restore previously unlocked paired apps. We added a an optional(as the reviewer suggested) sign in with Apple support if the user wants to secure their unlocked installations. Then we got rejected for forcing account creation, data collection and no ability to delete the account. Forcing account creation is false but maybe the reviewer was confused therefore we put explicit explanation under the sign in with Apple button noting that this is optional, reduced the required profile details to 0 for sign in with Apple and added very simple account deletion UI that is displayed on the same screen where the user sign in with Apple. And yet we get another rejection about forcing the users to create account to be able to do iAP(factually false) and that we don't have account deletion feature(again factually false). How to handle that? I have no idea how to fix issues that don't exist. I also run out of space for explaining the reviewer how things work in the app and this is an extremely simple app that does have exactly 2 views, one to scan the devices to connect and one to do playback on those devices and purchase the full version of the app to remove limits on playback.

Hi everyone, I'm reaching out to see if anyone else is experiencing unusually long review times, and hoping for some guidance from Apple staff who monitor these forums. My situation: I submitted KongFu Mahjong (3.0 for iOS, 1.0 for macOS) for review on February 11, 2026 — now 72 days ago. After requesting an expedited review, I received confirmation on March 2 that it was approved for the expedite queue. I followed up again on March 23 by both email and phone. Each time I was told to keep waiting. As of today, April 24, there has been no review, no rejection, and no feedback of any kind. The app simply sits in "In Review" status with complete silence. I spoke with Apple Developer Support by phone, and they confirmed this is not specific to my app — they acknowledged a long backlog. But 53 days in an expedited queue with zero communication feels like something may have fallen through the cracks. What I've tried: Expedited review request (approved March 2) Follow-up email and phone call (March 23) Follow-up email (April 24) My questions: Is anyone else seeing multi-month review times in early 2026? Is there a way to verify that a submission hasn't been lost or stuck in a system error? 3. Is there a more effective escalation path beyond Developer Support and the Resolution Center? I want to be clear — I'm not asking to skip the line. I just want to know my app is actually in a queue and hasn't been forgotten. I have several other apps ready to submit and this experience is making it very difficult to plan. Any advice or shared experiences would be appreciated.

We've a game that the first version has published 45 days again with a quick review and direct approve. After that initial version, we've made some big updates and additions as well as some bug fixes to get ready to officially publish our game, and market it. However, with my first update, it waited in the review queue for 2 weeks, which I then cancelled, make some bug fixes, and sent to review again since I heard that this can fix the process sometimes. Even after that, we've been waiting for 3 weeks and still no updates. I've also applied for Expedited Review since this is getting urgent after waiting more than a month. I hope someone from Apple Support team will see this and help me with the issue.

Hello everyone, I’m facing an issue with my app "FindUWay" (iOS), and I’m trying to understand if this is related to EU Digital Services Act (DSA) compliance. Current situation: App is approved and published on the App Store All agreements, tax forms (including W-8BEN), and banking info are completed and active App is set to be available in 175 countries, including Malta Issue: The app is NOT available in Malta and shows "App Not Available" on multiple iPhones and Apple IDs. Important detail: In App Store Connect, the only pending item is: Digital Services Act (DSA) compliance → Status: "In Review" since April 5th What I’ve observed: The app works and appears normally in some regions In Malta (EU), it does not open or install properly This seems to affect multiple devices (including iPhone 17 Pro Max) Questions: Is DSA compliance review blocking app availability in EU countries? Is it expected for the app to be unavailable while DSA is still "In Review"? Is there anything else I need to configure or submit? Has anyone experienced delays with DSA review recently? This is impacting my app launch, so any help or insight would be greatly appreciated. Thank you!

Case no: 102870409704 If 90% of apps are reviewed within 24 hours, why is my app taking over 2 weeks and still not in the review process? As I submitted my app on April 6th, the review time is very long though

Our app PrepAiro: Crack UPSC IAS 2026 (Account: 6741750813) has been caught in a rejection/resubmission loop since April 12, now over 10 days. Timeline: April 12: First rejection received Cycles 1–6: Each rejection addressed per reviewer feedback, resubmitted promptly April 18: Status moved to "Waiting for Review" , no movement since We submitted an expedited review request through Apple Support due to the urgency. This release contains critical bug fixes actively impacting users, but there has been no response or update. We understand review timelines can vary, but 6 full cycles over 10 days with no resolution, and a 6-day stall after the last submission, is unusual. Each resubmission addressed the specific feedback provided, yet the cycle continues. Has anyone experienced similar extended holds recently? And is there any additional channel or escalation path beyond the expedited review request to get clarity on what's causing this? Any guidance from Apple or fellow developers would be appreciated.

App Review stuck/stalled — Khalas (App ID 6757966927 Version 1.0.5 - ESCALATION) My app has been blocked in review far longer than usual, and previous channels have not resolved it. My app has an error and I need to roll back and release a fix and I can't because of this review problem. App Name: Khalas Apple ID (App Store Connect): 6757966927 Bundle ID: com.khalas.mobile.khalasapp2 Platform: iOS Team ID: AW8RAKXM5P Submission / review Version submitted for review: [1.0.5] Build number: 19 Current status in App Store Connect: In Review and previously stuck in “Waiting for Review” for over a week Total time in review pipeline: Over 7 days What I’ve already tried Requested Expedited App Reviewl Contacted Developer / App Review support Confirmed there are no unanswered messages in Resolution Center and no missing metadata on my side that I can see. Ask Please look up this submission by App ID 6757966927 and tell me whether: The review is actually active or blocked internally (queue, metadata sync, IAP attachment, etc.), There is a silent hold, duplicate submission, or binary processing issue, Anything specific you need from me (I’ve included identifiers above to avoid back-and-forth). I rely on this CRITICAL release and I’m doing everything I can on my side. I’m asking for a concrete status and, if possible, forward progress on this submission. Thank you

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Hi everyone, I’m trying to fix an App Review rejection related to auto‑renewable subscriptions, and I’m also blocked because my subscriptions don’t work in the sandbox even though configuration looks correct. App Review details App version: 3.5.3 Review device: iPhone 17 Pro Max iOS: 26.4 Guidelines: 3.1.2(c) and 2.1(b) Reviewer message says: Missing required subscription metadata links: Terms of Use (EULA) link in App Description (or custom EULA set in App Store Connect) Privacy Policy link in the Privacy Policy field in App Store Connect IAP bug / error during purchase (sandbox testing during review) What I see in App Store Connect My subscription products show “Developer Action Needed”. Subscription group/products are created (monthly + yearly). I believe all required subscription info is filled out (pricing, localization, etc.), but sandbox purchases still fail. Sandbox behavior / issue In Sandbox on device, attempting to purchase or load products results in an error on IAP (reviewer didn’t provide the exact error text). I’m using StoreKit (happy to share whether it’s StoreKit 1 vs StoreKit 2 if that matters) and fetching products by product IDs. Additional blocker: Banking info stuck “Processing” In App Store Connect → Agreements, Tax, and Banking, my banking section shows: “Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then.” But the banking status has stayed Processing for more than 2 weeks and never changes. I don’t know how to resolve this, and I suspect it might be related to why subscriptions are failing in sandbox / showing “Developer Action Needed”. Questions: What are the most common reasons subscriptions show “Developer Action Needed” and are rejected/blocked even when the setup seems complete? For Guideline 3.1.2(c): what is the correct place/best practice to provide the required links? Put Apple Standard EULA link in App Description? Add custom EULA in App Store Connect → App Information → EULA? Add Privacy Policy URL in App Store Connect Privacy Policy field (or the dedicated Privacy Policy URL field)? For the sandbox IAP error during review: Could this be caused by agreements / banking stuck in Processing or Paid Apps Agreement not active/accepted (even though the app is free but uses subscriptions)? Can “Developer Action Needed” prevent sandbox transactions from working for reviewers and my tests? Any recommended step-by-step checklist to validate subscriptions end-to-end (agreements, banking/tax, subscription metadata, product status, storefront, etc.)? Has anyone seen banking updates stuck in Processing for weeks? What is the best way to resolve it (waiting, re-submitting banking info, contacting Apple, specific support channel)?

Hi, my app (App ID: 6758626744, Team ID: H4DH43B9X7) has been stuck in a review cycle for 10 days, after flagged it in expedite. i had no answer so far, and we missed already an important financial deadline please help us review it asap

Hello, I would like to check the status of my app, as it has been stuck in review for a while (ID: 6746933136). Thank you

Hi everyone, I'm hoping someone here has experienced something similar or can offer some guidance, as I'm running out of ideas. I've been an Apple Developer for about 7 months. This is my first app submission, I submitted it on March 24, 2026, and it has been sitting at "Waiting for Review" ever since. 32 days now with no movement. What I've already checked and confirmed: All agreements, tax, and banking information are fully completed in App Store Connect No issues visible in the AppStore Connect DSA trader verification has been approved (I'm based in EU) I contacted Developer Support and they confirmed they can see my submission and that it is indeed "Waiting for Review" since March 24th An expedited review request was submitted and accepted by the support team, who told me the review should begin "shortly" - that was several weeks ago Additional context: During the 7 months I've been a developer, none of my TestFlight external review requests ever went through either, which makes me wonder if there is something on the account level causing holds I have not made any changes to the binary since submitting, to protect my position in the queue There are no rejection notices, no metadata issues, and no communication from the review team I understand new developer accounts take longer and I've been patient, but 32 days with an accepted expedited request and still no movement feels beyond normal variance. I'm genuinely unsure if there is something silently blocking my account that I'm not aware of. Has anyone experienced this, particularly as a new developer? Any advice on further escalation would be really appreciated. Thank you

App Review stuck/stalled — Khalas (App ID 6757966927 Version 1.0.5 - ESCALATION) My app has been blocked in review far longer than usual, and previous channels have not resolved it. My app has an error and I need to roll back and release a fix and I can't because of this review problem. App Name: Khalas Apple ID (App Store Connect): 6757966927 Bundle ID: com.khalas.mobile.khalasapp2 Platform: iOS Team ID: AW8RAKXM5P Submission / review Version submitted for review: [1.0.5] Build number: 19 Current status in App Store Connect: In Review and previously stuck in “Waiting for Review” for over a week Total time in review pipeline: Over 7 days What I’ve already tried Requested Expedited App Reviewl Contacted Developer / App Review support Confirmed there are no unanswered messages in Resolution Center and no missing metadata on my side that I can see. Ask Please look up this submission by App ID 6757966927 and tell me whether: The review is actually active or blocked internally (queue, metadata sync, IAP attachment, etc.), There is a silent hold, duplicate submission, or binary processing issue, Anything specific you need from me (I’ve included identifiers above to avoid back-and-forth). I rely on this CRITICAL release and I’m doing everything I can on my side. I’m asking for a concrete status and, if possible, forward progress on this submission. Thank you

Hello, I'm posting again because my situation has not improved despite previous outreach. My app (ID: 6756186616, iOS 1.3.0) was submitted on March 15, 2026 — over 6 weeks ago. After about 4 weeks in "Waiting for Review," it moved to "In Review" on April 14, 2026. It has now been stuck in "In Review" for two full weeks with no further updates. I opened a Developer Support case (#20000111565861) earlier in the process and was told my submission was being investigated, but I have not received any follow-up communication since. Given Apple's stated review timelines, a 6+ week review with two weeks of silence during the active In Review phase is a serious blocker for an independent developer. I would really appreciate: Any clarity on whether something specific in my submission is causing this delay Whether there is an escalation path beyond Developer Support Whether anyone else has experienced similar timelines recently and how they were resolved Thank you for your time.

Hi there everyone, I submitted an app nearly a month and a half ago now and it took a whole month for it to be reviewed. Once reviewed, I thought the process would then speed up and I would have continuous contact with the reviewer reviewing my app. However, it has now been over 2 weeks since I resubmitted my app. Is this normal? Does anybody know how long this may take? Please let me know.

Our app Heat Game (iOS, version 1.15.0) has been in the "In Review" status since April 18th. We have received no feedback, rejections, or communication from the App Review team for over 10 days, despite a "last touched" update on April 22nd. Submission Timeline: Submitted: April 17, 2026 In Review since: April 18, 2026 Last Activity: April 22, 2026 Current State: IN_REVIEW (No metadata issues or rejections flagged) Why this is critical: This is not a routine feature update. Version 1.15.0 contains critical fixes for broken payment flows currently live in the production version. These bugs are actively preventing users from completing purchases, leading to: Direct Revenue Loss: Significant daily financial impact on our operations. Steps taken so far: We have already reached out via the App Store Connect Resolution Center, but have not received a substantive response. Request to Community/Apple: Has anyone successfully escalated a review specifically for time-sensitive, revenue-blocking bugs? Beyond the Resolution Center, are there documented channels or specific keywords that help flag a case for "Expedited Review" when it involves significant business impact? We appreciate any guidance or assistance the community or Apple staff can provide.

I am unable to submit any app for review. Every attempt to add a build to an App Store version results in a 409 error, both through the App Store Connect website and directly through the App Store Connect REST API. Affected accounts: Account 1: My personal Apple Developer account Account 2: A company-owned Apple Developer account where I have Admin access Both accounts are completely separate — different legal entities, different enrollments — but exhibit the exact same behavior simultaneously. API errors observed When calling PATCH /v1/appStoreVersions/{id}/relationships/build: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "The specified pre-release build could not be added." When calling POST /v1/appStoreVersions to create a new version: 409 ENTITY_ERROR.RELATIONSHIP.INVALID "You cannot create a new version of the App in the current state." What I have verified All builds are processingState: VALID and not expired usesNonExemptEncryption: false is set on all builds No build is already attached to another version Build version string matches the App Store version (1.1.0) App bundle ID matches the build bundle ID Localization, review contact details, and keywords are all filled in Banking info in Agreements, Tax, and Banking was recently updated on both accounts Issue persists on both the website and via the REST API, ruling out a browser/cache issue Question Has anyone seen 409 errors affecting two completely separate developer accounts simultaneously? Could there be a platform-level issue with App Store Connect that is not reflected on the System Status page? I opened a support ticket 1 week ago but I only got a reply today and it's just asking for more details.

Hello, I'm hoping someone from Apple or the community can help me get some clarity on my situation. Two months ago, my app was rejected by App Review, and I immediately filed a formal appeal. Since then, I have received absolutely no response — not an acknowledgment, not a status update, nothing. In the meantime, I have also reached out to Apple Developer Support via email on multiple occasions. Again, no response of any kind. I understand that review and appeal timelines can vary, but two months of complete silence — across both the appeal process and direct support emails — makes it very difficult to know whether my case is even being reviewed or if something has fallen through the cracks. If anyone from the App Review team or Apple Developer Relations sees this, I would appreciate any guidance you can offer. And if any developers have been in a similar situation, I'd like to know what worked. Thank you.

I set up all the App Store details, including support info and other required information, but I’m having an issue when adding a build and trying to save. The Save button turns red, and I’m not sure why. It’s not showing what I’m missing in the setup.

Is anyone have issues with builds not appearing under the Build section in itunesconnect?I've successfully submitted multiple builds, but the builds do not appear in itunesconnect. I know that it's in the system because when I try to upload a build with the same version and build number, it errors out saying the version has already been uploaded.